***Turn Word Wrap on***

Hello fellow Stevens pilots,

welcome to the extensive STV AI Pack which brings every aircraft (except the Concorde) in the fleet to you as AI traffic. 

First of all, I would like to thank Dennis Mangold for his initiative and all the work he has done in order to make this package possible. He has painted the entire STV AI fleet- Models and paintkits used are from AI Aardvark and FSPainter (MD11). Thank You, Dennis!

Based on our aircraft rotations, we've built flightplans for compilation of every aircraft in the fleet. Our B732 D-AGAM follows a personal flightplan of mine, representative of its charter operation.

You will find an individual traffic file per aircraft. The logic behind this is that before going on a flight you can disable the traffic file for the aircraft you intend to use by renaming the file from "Traffic_STV_D-ASMA.bgl" to i.e. "Traffic_STV_D-ASMA.bgl.bak"
That way, the aircraft you are flying yourself will definitely not appear next to you on the apron - realism can be cruel ;-)


In the traffic file folder of the package you will see that we have compiled traffic files for FS9 and FSX. (FS9 users pls. use the FS9 files only).

ATTENTION FSX users!!!:
FSX demonstrates a strange behaviour with regards to AI traffic files. It does not permit mixing of FS9 native files and FSX native files!

In case you have FS9 native traffic files (i.e. from World of AI) and add FSX native traffic files, the FSX ones will not be displayed! (FSX gives priority to the FS9 files in this case - go figure...)

You have 2 options:
1. Stick to FS9 native files
2. Migrate all FS9 files to FSX native

The extraordinary tool AI Flight Planner (http://members.shaw.ca/aifp/) which we used to compile the bgls has a feature that permits FSX users to search for FS9 native traffic files and convert them to FSX format.

B767 Winglet modification program:
As you know we have started a conversion program to add winglets to our B767-fleet. This AI package represents the current status, meaning only D-ASTA has been fitted with winglets. As you know, a winglet modification is a serious investment (approx. 2-3M USD) and since a significant amount of man hours go into these conversions, the work is usually carried  out as part of C- or D-Checks. As a result, the rest of our 767 fleet will be converted towards the end of 2011 / beginning of 2012. Therefore only D-ASTA has winglets in this package. We will update the AI package as we go...

CONCORDE:
Unfortunately we can not include our Concorde D-ASAP in the AI package. The reason being that the only AI Concorde available for AI (from ARNZ) does not provide a public paintkit. Therefore we can not offer "legal" STV textures.

AFCAD:
Please note that most Stevens aircraft are in the "heavy" category. If your AFCAD file for any Stevens destination does not feature a "heavy"-gate, the aircraft will NOT show up.Your AFCAD should specify gates for Stevens aircraft with parking code "STV", so that they will try to park there. Cargo planes (744F and MD-11) use the parking code "STVC" . Pls. make sure your AFCADs at EDDK and other STV destinations use these parking codes. I have attached my EDDK AFCAD modification to the package.

Note also that RJGG (Nagoya Chu-bu Centrair Intl., Japan) and VTBS (Bangkok Suvarnabhumi Intl., Thailand) are no standard sceneries in FS2004. Unless you have installed sceneries for these, flights headed for or originating from these two destinations will not show up.

SPARE AIRCRAFT:
Stevens, like all major airlines, maintains two spare aircraft to accomodate for network flexibilty. In the current aircraft rotation plan, we have assigned D-ASSI and D-ASCD for Cargo as our spare aircraft. As part of our fleet planning however we will return D-ASSS to the lessor and have the deferred the pending D-Check. Until the aircraft is returned she will act as spare aircraft and SI will assume the rotations of SS. 
For our spare AI we have created a weekly flight to Hahn airport and back. As a result they do not regularly fly, and since parking at EDDK can get tight, I suggest you designate two remote parking positions on your EDDK AFCAD which should be assigned with parking codes "ASSI" and "ASCD". As a result the aircraft will park at these remote positions and will not block any gates. EDDK offers two positions suitable for this. One is a remote pad north of taxiway D nearby the runway 24 threshold. The other one is the run-up hall near by parking positions V10-V12. 
My EDDK AFCAD (for Aerosoft EDDK scenery - sorry FS9 only here) adds these positions and a couple of other features (see separate readme)...


INSTALLATION:
FS9:
Extract all aircraft folders into your "/Flight Simulator 9/aircraft"-folder.
All traffic .bgl files go into your "/Flight Simulator 9/scenery/world/scenery"-folder.
The AFCAD goes into the corresponding scenery folderfor EDDK. Make a backup of your current AFCAD!!!

FSX:
I don't have FSX, but I'm sure the FSX folks know where the aircraft and .bgl stuff goes.


Disclaimer:
Distributed as is. We are not responsible for any issues on your system - you should be familiar with FS AI installations and folder structures. 
Aircraft textures painted by Dennis Mangold, copyright Dennis Mangold, flightplans created and compiled by Kris Gamaggio.


Enjoy!

Regards,
Dennis and Kris

March 2011